Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

actions/sync/shared-config: update Gemfile.lock if it exists. #128

Merged
merged 1 commit into from
Jun 11, 2024

Conversation

MikeMcQuaid
Copy link
Member

This avoids the need to manually update this file in every repository.

@MikeMcQuaid MikeMcQuaid force-pushed the update_gemfile_lock branch 3 times, most recently from f405fc4 to 3e7227a Compare June 11, 2024 13:40
This avoids the need to manually update this file in every repository.
@MikeMcQuaid MikeMcQuaid merged commit af4d02a into master Jun 11, 2024
29 checks passed
@MikeMcQuaid MikeMcQuaid deleted the update_gemfile_lock branch June 11, 2024 13:43
if (target_directory_path/"Gemfile.lock").exist?
Dir.chdir target_directory_path do
puts "Running bundle install..."
system "bundle install --quiet >/dev/null"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

bundle update --ruby should be cheaper.

Could also maybe pass --bundler too to update the locked bundler version used.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants